Hosting network manual selection and ue-triggered registration update

ABSTRACT

A method of enhanced manual network selection procedure for access localized services in PNI-NPN is proposed. For manual CAG/PNI-NPN selection as hosting network, if a CAG cell in a PLMN broadcasting a CAG-ID is available and included in the (Allowed) CAG-ID list of the UE-stored CAG related configuration of the PLMN, the user may manually select the CAG cell as a suitable cell. However, the CAG-ID that is associated with validity information, and the corresponding validity criteria may or may not be satisfied, e.g., due to the UE-stored CAG related configuration is different from the NW-maintained CAG related configuration. Therefore, the UE does not know whether the CAG cell is suitable. In response, the UE triggers a registration procedure for mobility and periodic registration update, and obtains the updated CAG related configuration.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 119 from U.S. Provisional Application No. 63/336,368, entitled “Local Service Provided by NPN (PNI-NPN or SNPN-NPN) (NPN for localized services)”, filed on Apr. 29, 2022, the subject matter of which is incorporated herein by reference.

TECHNICAL FIELD

The disclosed embodiments relate generally to wireless mobile communication network, and, more particularly, to methods for UE performing manual network selection when supporting accessing CAG/PNI-NPN as hosting network for Localized services.

BACKGROUND

A Public Land Mobile Network (PLMN) is a network established and operated by an administration or recognized operating agency (ROA) for the specific purpose of providing land mobile communication services to the public. PLMN provides communication possibilities for mobile users. A PLMN may provide service in one or a combination of frequency bands. Access to PLMN services is achieved by means of an air interface involving radio communications between mobile phones and base stations with integrated IP network services. One PLMN may include multiple radio access networks (RAN) utilizing different radio access technologies (RAT) for accessing mobile services. A radio access network is part of a mobile communication system, which implements a radio access technology. Conceptually, RAN resides between a mobile device and provides connection with its core network (CN). Depending on the standard, mobile phones and other wireless connected devices are varyingly known as user equipment (UE, i.e., MS), terminal equipment (TE), mobile stations (MS, i.e., UE), mobile termination (MT), etc. Examples of different RATs include 2G GERAN (GSM) radio access network, 3G UTRAN (UMTS) radio access network, 4G E-UTRAN (LTE), 5G new radio (NR) radio access network, NG-RAN (Next-Generation RAN), and other non-3GPP access RAT including WiFi.

As compared to PLMN, a non-public network (NPN) is a network for non-public use. An NPN is either a Stand-alone Non-Public Network (SNPN), i.e., operated by an NPN operator and not relying on network functions provided by a PLMN; or a Public Network Integrated NPN (PNI-NPN), i.e., a non-public network deployed with the support of a PLMN. A Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder. The combination of a PLMN ID and Network identifier (NID) identifies an SNPN. A UE may be enabled for SNPN.

PNI-NPNs are NPNs made available via PLMNs e.g., by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN. When a PNI-NPN is made available via a PLMN, then the UE shall have a subscription of the PLMN in order to access PNI-NPN. As network slicing does not enable the possibility to prevent UEs from trying to access the network in areas where the UE is not allowed to use the Network Slice allocated for the NPN, Closed Access Groups can be used to apply access control for PNI-NPN. A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). CAG is used for access control e.g., authorization at cell selection and configured in the subscription as part of the Mobility Restrictions. A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID.

Local or Localized services are services that are localized (e.g., provided at specific/limited area and/or are bounded in time). A localized service provider is an application provider or a network operator who make their services localized and to be offered to end user via a hosting network. A hosting network is a network that provides (access for) Localized services, and a hosting network can be an SNPN or a PNI-NPN, while a home network is network owning the current in use subscription or credential of the UE. Home network can be either Home-PLMN or Subscribed-SNPN. End user can enable or disable to access Localized services. If the end user disables to access Localized services, the UE(i.e., MS) may not access an NPN providing access for Localized services.

For providing (access for) Localized services to UE, UE needs to be able to discover, select and access an NPN (as hosting network) providing access for Localized services.

SUMMARY

A method of enhanced manual network selection procedure for access localized services in PNI-NPN is proposed. For manual CAG/PNI-NPN selection as hosting network, if a CAG cell in a PLMN broadcasting a CAG-ID is available and included in the (Allowed) CAG-ID list of the UE-stored CAG related configuration of the PLMN, the user may manually select the CAG cell as a suitable cell. However, the CAG-ID that is associated with validity information, and the corresponding validity criteria may or may not be satisfied, e.g., due to the UE-stored CAG related configuration is different from the NW-maintained CAG related configuration. Therefore, the UE does not know whether the CAG cell is suitable. In response, the UE triggers a registration procedure for mobility and periodic registration update, and obtains the updated CAG related configuration.

Other embodiments and advantages are described in the detailed description below. This summary does not purport to define the invention. The invention is defined by the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 schematically shows a communication system having a Public Land Mobile Network (PLMN), a Stand-alone Non-public Network (SNPN), and a Public Network Integrated NPN (PNI-NPN) supporting (hosting) network and cell selection with Localized services in accordance with one novel aspect.

FIG. 2 illustrates simplified block diagrams of a user equipment and a network entity in accordance with embodiments of the current invention.

FIG. 3A illustrates a first embodiment of a 5G system architecture with access to SNPN using credentials from credentials holder.

FIG. 3B illustrates a second embodiment of a 5G system architecture with access to SNPNs using credentials from credentials holder.

FIG. 4 illustrates an example of NG-RAN modes which broadcast certain information in order to provide access to SNPNs.

FIG. 5A illustrates an example of an SNPN-enabled UE that is configured with 2 SNPN subscriptions (i.e., 2 subscribed SNPNs in the “list of subscriber data”).

FIG. 5B illustrates an example of an SNPN-enabled UE that is configured with 2 PLMN subscriptions (i.e., 2 USIMs).

FIG. 6 illustrates Network selection in SNPN access mode with automatic SNPN network selection and manual SNPN network selection.

FIG. 7A illustrates a first embodiment of network and cell selection and access control of CAG cells for PNI-NPN (CAG), where access to a CAG cell is accepted.

FIG. 7B illustrates a second embodiment of network and cell selection and access control of non-CAG cells (public cells), where access to a PLMN is accepted.

FIG. 8A illustrates a first embodiment of network and cell selection and access control of CAG cells for PNI-NPN (CAG), where access to a CAG cell is rejected.

FIG. 8B illustrates a second embodiment of network and cell selection and access control of non-CAG cells (public cells), where access to a PLMN is rejected.

FIG. 9A illustrates one example of UE to discover, select and access NPN (as hosting network) providing access for Localized services using validity information.

FIG. 9B illustrates another example of UE to discover, select and access NPN (as hosting network) and receive localized services using validity information associated with an SNPN.

FIG. 9C illustrates different examples of UE to discover, select and access NPN (as hosting network) and receive localized services using validity information associated with a CAG (of a PLMN).

FIG. 10A illustrates a first example of accessing SNPN (as a hosting network) providing access for Localized services, where access is accepted.

FIG. 10B illustrates a second example of accessing SNPN (as a hosting network) providing access for Localized services, where access is rejected.

FIG. 11A illustrates a first example of accessing PNI-NPN/CAG (as a hosting network) providing access for Localized services, where access is accepted.

FIG. 11B illustrates a second example of accessing PNI-NPN/CAG (as a hosting network) providing access for Localized services, where access is rejected.

FIG. 12 illustrates a sequence flow between a UE and a PLMN network for performing manual network selection, where the UE selects a CAG/PNI-NPN as hosting network and triggers a mobility and periodic registration update procedure.

FIG. 13 illustrates examples of a Manual Network Selection Mode Procedure that is triggered by user, and the user manually selects a CAG/PNI-NPN candidates as hosting network for localized services.

FIG. 14 is a flow chart of a method for Manual Network Selection when user selects a CAG/PNI-NPN as hosting network and triggers registration update procedure in accordance with one novel aspect.

DETAILED DESCRIPTION

Reference will now be made in detail to some embodiments of the invention, examples of which are illustrated in the accompanying drawings.

FIG. 1 schematically shows a communication system 100 having a Public Land Mobile Network (PLMN) 110, a Stand-alone Non-public Network (SNPN) 120, and a Public Network Integrated NPN (PNI-NPN)/CAG 130 providing access for Localized services in accordance with one novel aspect. PLMN network 110 comprises control plane functionalities, user plane functionality (e.g., UPF), and applications that provides various services by communicating with a plurality of user equipments (UEs) including UE 101. Serving base station gNB 112 belong to part of a radio access network RAN 140. RAN 140 provides radio access for UE 101 via a radio access technology (RAT). An access and mobility management function (AMF) in PLMN 110 communicates with gNB 112. UE 101 may be equipped with a radio frequency (RF) transceiver or multiple RF transceivers.

SNPN network 120 comprises control plane functionalities, user plane functionality (e.g., UPF), and applications that provides various services by communicating with a plurality of user equipments (UEs) including UE 101. The combination of a PLMN ID and Network identifier (NID) identifies an SNPN. Serving base station gNB 122 belongs to part of RAN 150. RAN 150 provides radio access for UE 101 via a RAT. An AMF in SNPN 120 communicates with gNB 122. SNPN 120 is operated by an NPN operator and does not rely on network functions provided by a public network. A Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder. NG-RAN nodes which provide access to SNPNs broadcast the following information: One or multiple PLMN IDs, and a List of NIDs per PLMN ID identifying the non-public networks NG-RAN provides access to (123). An SNPN-enabled UE is configured with PLMN ID and NID (SNPN ID) of the subscribed SNPN, and an SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder may additionally be configured with information for SNPN selection (SNPN selection information or configuration) and registration using the SNPN subscription or using PLMN subscription (USIM) (in SNPN access mode) (102).

PNI-NPN (CAG) network 130 comprises control plane functionalities (optional, it may rely on PLMN's control plane functionality), user plane functionality (optional, it may rely on PLMN's user plane functionality), and applications that provides various services by communicating with a plurality of user equipments (UEs) including UE 101. PNI-NPN (CAG) 130 is a non-public network deployed with the support of a PLMN, e.g., PLMN 110, by sharing e.g., RAN/gNB 112 and e.g., control plane functionalities. A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID. A CAG cell broadcasts one or multiple CAP Identifiers per PLMN (113), and a UE is configured with CAG related configuration/information. (e.g., an (enhanced) CAG information list containing list of allowed CAGB per PLMN) (102).

Local or Localized services are services that are localized (i.e., provided at specific/limited area and/or are bounded in time (a specific period of time)). A localized service provider is an application provider or a network operator who makes their services localized and to be offered to end user via a hosting network. A hosting network is a network that provides access for localized services and can be an SNPN or a PNI-NPN, while a home network is network owning the current in use subscription or credential of the UE. In the example of FIG. 1 , both SNPN 120 and PNI-NPN (CAG) 130 can be a hosting network providing access for Localized services to UE 101.

A URSP rule may include an association of the UE application and the DNN or network slice which is meant for a specific localized service. A URSP rule can also include “Route Selection Validity Criteria” (Time Window and/or a Location Criteria Validity Conditions) with the time/location defined for the specific localized service. The LADN (Local Access Data Network) can also be used for enabling the UE access to localized service.

To enable a PNI-NPN or SNPN to provide access to localized services, the PNI-NPN or SNPN operator configures the network with information enabling the UEs to access the localized services according to validity of the localized services, and the information is determined in agreement with the localized service provider, e.g.: (a) Identification of each localized service, e.g. to be used in URSP rules; (b) validity criteria/restriction for each localized service, e.g., the validity of time duration and/or (area of) location.

When localized services in a network are completed, all UEs registered with the network are expected to be moved to other network or to other cells within the same network. The other network can be HPLMN, VPLMN or another SNPN. UE can stop using the network resources for localized services for numerous reasons, e.g.: (a) Localized services in a network are completed; (b) Validity conditions of network selection information are no longer met; (c) The user decides to stop using the localized services before they are completed (e.g., end user disables to access Localized services); (d) A policy decision is taken by the network, with the effect that the UE is deregistered before the localized services are completed. Validity information or restrictions or criteria or conditions (103) are provided or configured to UE as part of the localized service information, which are used to restrict the UE's access of the SNPN/PNI-NPN (as hosting network) providing access for Localized services. For providing localized services to UE, UE needs to be able to discover, select and access a SNPN/PNI-NPN (as hosting network) providing access for the Localized services. The discovery mechanism is based on provisioning or configuring the UE with appropriate information.

FIG. 2 illustrates simplified block diagrams of wireless devices, e.g., a UE 201 and network entity 211 in accordance with embodiments of the current invention. Network entity 211 may be a base station combined with an AMF. Network entity 211 has an antenna 215, which transmits and receives radio signals. A radio frequency RF transceiver module 214, coupled with the antenna, receives RF signals from antenna 215, converts them to baseband signals and sends them to processor 213. RF transceiver 214 also converts received baseband signals from processor 213, converts them to RF signals, and sends out to antenna 215. Processor 213 processes the received baseband signals and invokes different functional modules to perform features in base station 211. Memory 212 stores program instructions and data 220 to control the operations of base station 211. In the example of FIG. 2 , network entity 211 also includes a set of control functional modules and circuit 290. Registration circuit 231 handles registration and mobility procedure. Session management circuit 232 handles session management functionalities. Configuration and control circuit 233 provides different parameters to configure and control UE.

Similarly, UE 201 has memory 202, a processor 203, and radio frequency (RF) transceiver module 204. RF transceiver 204 is coupled with antenna 205, receives RF signals from antenna 205, converts them to baseband signals, and sends them to processor 203. RF transceiver 204 also converts received baseband signals from processor 203, converts them to RF signals, and sends out to antenna 205. Processor 203 processes the received baseband signals and invokes different functional modules and circuits to perform features in UE 201. Memory 202 stores data and program instructions 210 to be executed by the processor to control the operations of UE 201. Suitable processors include, by way of example, a special purpose processor, a digital signal processor (DSP), a plurality of micro-processors, one or more micro-processor associated with a DSP core, a controller, a microcontroller, application specific integrated circuits (ASICs), file programmable gate array (FPGA) circuits, and other type of integrated circuits (ICs), and/or state machines. A processor in associated with software may be used to implement and configure features of UE 201.

UE 201 also comprises a set of functional modules and control circuits to carry out functional tasks of UE 201. Protocol stacks 260 comprise Non-Access-Stratum (NAS) layer to communicate with an AMF entity connecting to the core network, Radio Resource Control (RRC) layer for high layer configuration and control, Packet Data Convergence Protocol/Radio Link Control (PDCP/RLC) layer, Media Access Control (MAC) layer, and Physical (PHY) layer. System modules and circuits 270 may be implemented and configured by software, firmware, hardware, and/or combination thereof. The function modules and circuits, when executed by the processors via program instructions contained in the memory, interwork with each other to allow UE 201 to perform embodiments and functional tasks and features in the network. In one example, system modules and circuits 270 comprise registration circuit 221 that performs registration and mobility procedure with the network, a network and cell selection circuit 222 for performing network and cell selection, a PLMN/PNI-NPN(CAG)/SNPN information maintenance circuit 223 that handles the adding, removing, and resetting of one or more PLMN/PNI-NPN(CAG)/SNPN information in SIM/USIM and/or in UE (non-volatile) memory (source of the information may come from signaling as well), a config and control circuit 224 that handles configuration and control parameters. Note that the network selection and registration related information, such as HPLMN, Operator Controlled PLMN/SNPN Selector list, User Controlled PLMN/SNPN Selector list, may be stored in SIM/USIM 225 and/or in UE (non-volatile) memory.

SNPN

FIG. 3A illustrates a first embodiment of a 5G system architecture with access to SNPN using credentials from credentials holder. FIG. 3A depicts the 5G System architecture for SNPN with Credentials Holder using AAA Server for primary authentication and authorization. The AUSF and the UDM in SNPN may support primary authentication and authorization of UEs using credentials from a AAA Server in a Credentials Holder (CH). The SNPN in FIG. 3A can be the subscribed SNPN for the UE (i.e. NG-RAN broadcasts SNPN ID of the subscribed SNPN). As a deployment option, the SNPN in FIG. 3A can also be another SNPN than the subscribed SNPN for the UE (i.e. none of the SNPN IDs broadcast by NG-RAN matches the SNPN ID corresponding to the subscribed SNPN). The NSSAAF deployed in the SNPN can support primary authentication in the SNPN using credentials from Credentials Holder using a AAA Server (as depicted) and/or the NSSAAF can support Network Slice-Specific Authentication and Authorization with a Network Slice-Specific AAA Server (not depicted).

FIG. 3B illustrates a second embodiment of a 5G system architecture with access to SNPNs using credentials from credentials holder. FIG. 3B depicts the 5G System architecture for SNPN with Credentials Holder using AUSF and UDM for primary authentication and authorization and network slicing. An SNPN may support primary authentication and authorization of UEs that use credentials from a Credentials Holder using AUSF and UDM. The Credentials Holder may be an SNPN or a PLMN. The Credentials Holder UDM provides to SNPN the subscription data.

FIG. 4 illustrates an example of NG-RAN mode(s) which broadcasts certain information in order to provide access to SNPNs. A Credentials Holder (CH) may authenticate and authorize access to an SNPN separate from the Credentials Holder. For SNPN identification, the combination of a PLMN ID and Network identifier (NID) identifies an SNPN. The NID supports two assignment models. Under self-assignment model, NIDs are chosen individually by SNPNs at deployment time (and may therefore not be unique) but use a different numbering space than the coordinated assignment NIDs. Under coordinated assignment model, NIDs are assigned using one of the following two options: 1) The NID is assigned such that it is globally unique independent of the PLMN ID used; or 2) The NID is assigned such that the combination of the NID and the PLMN ID is globally unique.

The Group IDs for Network Selection (GIN) supports two assignment models. Under self-assignment model, GINs are chosen individually and may therefore not be unique. Under coordinated assignment model, GIN uses a combination of PLMN ID and NID and is assigned using one of the following two options: 1) The GIN is assigned such that the NID is globally unique (e.g., using IRNA Private Enterprise Numbers) independent of the PLMN ID used; or 2) The GIN is assigned such that the combination of the NID and the PLMN ID is globally unique.

In the example of FIG. 4 , NG-RAN 401 provides access to SNPNs and broadcasts the following information (410): One or multiple PLMN IDs and List of NIDs per PLMN ID identifying the non-public networks the NG-RAN provides access to (e.g., SNPN 1 and SNPN 2). Optionally, the broadcasted information further includes the following: a human-readable network name (HRNN) per SNPN; an indication per SNPN of whether access using credentials from a Credentials Holder is supported; a list of supported Group IDs for Network Selection (GINs) per SNPN (e.g., GIN 1 and GIN 2); and an indication per SNPN of whether the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e., UEs that do not have any SNPN ID (PLMN ID+NID) nor GIN broadcast by the SNPN in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs.

FIG. 5A illustrates an example of an SNPN-enabled UE that is configured with SNPN subscription information for each subscribed SNPN. In the example of FIG. 5A, an SNPN-enabled UE 501 is configured with the 2 SNPN subscriptions as depicted by 510/520 for each subscribed SNPN: SNPN ID (PLMN ID+NID) of the subscribed SNPN (e.g., SNPN 1 in Entry 1 of the “list of subscriber data”, SNPN 2 in Entry 2 of the “list of subscriber data”); and Subscription identifier (SUPI) and credentials for each of the subscribed SNPN. If the UE supports access to an SNPN using credentials from a Credentials Holder for each subscribed SNPN: 1) User controlled prioritized list of preferred SNPNs (e.g., SNPN 111, SNPN 112 for Entry 1; SNPN 211, SNPN 212 for Entry 2); 2) Credentials Holder controlled prioritized list of preferred SNPNs (e.g., SNPN 121, SNPN 122 for Entry 1; SNPN 221, SNPN 222 for Entry 2); and 3) Credentials Holder controlled prioritized list of GINs (e.g., GIN131, GIN132 for Entry 1; GIN 231, GIN 232 for Entry 2).

FIG. 5B illustrates an example of an SNPN-enabled UE that is configured with 2 PLMN subscriptions (i.e., 2 USIMs). An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription (USIM) may additionally be configured with information for SNPN selection and registration using the PLMN subscription (in SNPN access mode). For example, PLMN subscription 1 is associated with information for SNPN selection 530: 1) User controlled prioritized list of preferred SNPNs (e.g., SNPN 311, SNPN 312); 2) Credentials Holder controlled prioritized list of preferred SNPNs (e.g., SNPN 321, SNPN 322); and 3) Credentials Holder controlled prioritized list of GINs (e.g., GIN 331, GIN 332). Similarly, PLMN subscription 2 is associated with information for SNPN selection 540: 1) User controlled prioritized list of preferred SNPNs (e.g., SNPN 411, SNPN 412); 2) Credentials Holder controlled prioritized list of preferred SNPNs (e.g., SNPN 421, SNPN 422); and 3) Credentials Holder controlled prioritized list of GINs (e.g., GIN 431, GIN 432).

A subscription of an SNPN is either identified by a SUPI containing a network-specific identifier that takes the form of a Network Access Identifier (NAI). The realm part of the NAI may include the NID of the SNPN; or identified by a SUPI containing an IMSI. For an SNPN-enabled UE with SNPN subscription, the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs may be updated by the CH using the Steering of Roaming (SoR) procedure. For an SNPN-enabled UE with PLMN subscription, the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs may be updated by the CH using the Steering of Roaming (SoR) procedure. When the Credentials Holder updates a UE with the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, the UE may perform SNPN selection again, e.g., to potentially select a higher prioritized SNPN.

FIG. 6 illustrates Network selection in SNPN access mode with automatic SNPN network selection and manual SNPN network selection. An SNPN-enabled UE 601 supports to access SNPN (in SNPN access mode). When the UE is set to operate in SNPN access mode the UE only selects and registers with SNPNs. When a UE is set to operate in SNPN access mode the UE does not perform normal PLMN selection procedures. There are two SNPN network selection procedures: an automatic SNPN network selection procedure and a manual SNPN network selection procedure.

Under automatic SNPN network selection, UE selects and attempts registration on available and allowable SNPNs in the following order: 1) the SNPN the UE was last registered with (if available) or the equivalent SNPN (if available); 2) the subscribed SNPN, which is identified by the SNPN ID (PLMN ID+NID) for which the UE has SUPI and credentials; 3) if the UEs supports access to an SNPN using credentials from a Credentials Holder then the UE continues by selecting and attempting registration on available and allowable SNPNs which broadcast the indication that access using credentials from a Credentials Holder is supported in the following order: a) SNPNs in the user controlled prioritized list of preferred SNPNs (in priority order); b) SNPNs in the Credentials Holder controlled prioritized list of preferred SNPNs (in priority order); c) SNPNs, which additionally broadcast a GIN contained in the Credentials Holder controlled prioritized list of preferred GINs (in priority order); and 4) SNPNs, which additionally broadcast an indication that the SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, i.e. the broadcasted SNPN ID or GIN is not present in the Credentials Holder controlled prioritized lists of preferred SNPNs/GINs in the UE.

In the example of FIG. 6 , UE 601 was registered to SNPN 100, the subscribed SNPN is SNPN 1 and has three lists for credentials. The User controller prioritized list of preferred SNPNs includes SNPN 111, SNPN 112; the Credential Holder controlled prioritized list of preferred SNPNs includes SNPN 121, SNPN 122; the Credential Holder controlled prioritized list of GINs includes GIN 131, GIN 132. There are a list of SNPNs/GINs (broadcasted by one or more NG-RANs) available in current UE location e.g., SNPN 100, SNPN 1, SNPN 111, SNPN 112, SNPN 121, SNPN 300/GIN 131. UE 601 selects and attempts to register to an SNPN in the following preference/priority order: SNPN 100, SNPN 1, SNPN 111, SNPN 112, SNPN 121, and SNPN 300 which also broadcasts GIN 131.

Under manual network selection, UEs operating in SNPN access mode provide to the user the list of SNPNs (each is identified by a PLMN ID and NID) and related human-readable network names (if available) of the available SNPNs the UE has respective SUPI and credentials for. If the UEs supports access to an SNPN using credentials from a Credentials Holder, the UE also presents available SNPNs which broadcast the “access using credentials from a Credentials Holder is supported” indication and the human-readable names related to the SNPNs (if available). When a UE performs Initial Registration to an SNPN, the UE shall indicate the selected PLMN ID and NID as broadcast by the selected SNPN to NG-RAN. NG-RAN shall inform the AMF of the selected PLMN ID and NID.

If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a self-assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to temporarily prevent the UE from automatically selecting and registering with the same SNPN. If a UE performs the registration or service request procedure in an SNPN identified by a PLMN ID and a coordinated assigned NID and there is no subscription for the UE, then the AMF shall reject the UE with an appropriate cause code to permanently prevent the UE from automatically selecting and registering with the same SNPN. If a UE performs the registration in an SNPN using credentials from a Credentials Holder and UE is not authorized to access that specific SNPN, then the UDM can reject the UE which results in AMF rejecting the registration request from the UE with an appropriate cause code to prevent the UE from selecting and registering with the same SNPN using credentials from the Credentials Holder. In order to prevent access to SNPNs for authorized UE(s) in the case of network congestion/overload, Unified Access Control information is configured per SNPN (i.e., as part of the subscription information that the UE has for a given SNPN) and provided to the UE.

PNI-NPN (CAG)

PNI-NPNs (CAGs) are NPNs made available via PLMNs e.g., by means of dedicated DNNs, or by one (or more) Network Slice instances allocated for the NPN. The existing network slicing functionalities apply. When a PNI-NPN is made available via a PLMN, then the UE shall have a subscription for the PLMN in order to access PNI-NPN. A Closed Access Group (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. CAG is used for the PNI-NPNs to prevent UE(s), which are not allowed to access the NPN via the associated cell(s), from automatically selecting and accessing the associated CAG cell(s). A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID. A CAG cell broadcasts one or multiple CAG Identifiers per PLMN. A CAG cell may in addition broadcast a human-readable network name (HRNN) per CAG Identifier.

To use CAG, the UE, that supports CAG as indicated as part of the UE 5GMM Core Network Capability, may be pre-configured or (re)configured with the following CAG related information. If the UE supports CAG, the UE can be provisioned by the network with a CAG related configuration (e.g., (enhanced) CAG information (list) containing list of allowed CAGs per PLMN)), consisting of zero or more entries, each entry containing a) a PLMN ID, b) an “Allowed CAG list” having zero or more CAG-IDs, and c) an optional “indication that the UE is only allowed to access 5GS via CAG cells”. The HPLMN may (pre-)configure or re-configure a UE with the above CAG related configuration using the UE Configuration Update procedure or other 5GMM procedures (e.g., registration procedure or service procedure). The above CAG related configuration is provided by the HPLMN on a per PLMN basis. In a PLMN the UE shall only consider the CAG information provided for this PLMN.

When the subscribed CAG related configuration changes, UDM sets a CAG information Subscription Change Indication and sends it to the AMF. The AMF shall provide the UE with the CAG related configuration when the UDM indicates that the CAG related configuration within the Access and Mobility Subscription data has been changed. When AMF receives the indication from the UDM that the CAG related configuration within the Access and Mobility Subscription has changed, the AMF uses the CAG related configuration received from the UDM to update the UE. Once the AMF updates the UE and obtains an acknowledgment from the UE, the AMF informs the UDM that the update was successful and the UDM clears the CAG information Subscription Change Indication flag. The AMF may update the UE using either the UE Configuration Update procedure after registration procedure is completed, or by including the new CAG related configuration in the Registration Accept or in the Registration Reject or in the Deregistration Request or in the Service Reject.

When the UE is roaming and the Serving PLMN provides CAG related configuration, the UE shall update only the CAG related configuration provided for the Serving PLMN, while the stored CAG related configuration for other PLMNs is not updated. When the UE is not roaming and the HPLMN provides CAG related configuration, the UE shall update the CAG related configuration stored in the UE with the received CAG related configuration for all the PLMNs. The UE shall store the latest available CAG related configuration for every PLMN for which it is provided and keep it stored when the UE is de-registered or switched off. The CAG related configuration is only applicable with 5GS.

For network and cell selection, the CAG cell shall broadcast information such that only UEs supporting CAG are accessing the cell; cells are either CAG cells or normal PLMN cells (non CAG cells). For access control, in order to prevent access to NPNs for authorized UE(s) in the case of network congestion or overload, existing mechanisms defined for Control Plane load control, congestion and overload control can be used, as well as the access control and barring functionality, or Unified Access Control using the access categories can be used. The Mobility Restrictions shall be able to restrict the UE's mobility according to the Allowed CAG list (if configured in the subscription) and include an indication whether the UE is only allowed to access 5GS via CAG cells (if configured in the subscription).

During transition from CM-IDLE to CM-CONNECTED and during Registration after connected mode mobility from E-UTRAN to NG-RAN, the AMF shall verify whether UE access is allowed by Mobility Restrictions. If the UE is accessing the 5GS via a CAG cell and if at least one of the CAG Identifier(s) received from the NG-RAN is part of the UE's Allowed CAG list, then the AMF accepts the NAS request. If the UE is accessing the 5GS via a CAG cell and if none of the CAG Identifier(s) received from the NG-RAN are part of the UE's Allowed CAG list, then the AMF rejects the NAS request and the AMF can include CAG related configuration in the NAS reject message. The AMF then release the NAS signaling connection for the UE by triggering the AN release procedure. If the UE is accessing the 5GS via a non-CAG cell and the UE's subscription contains an indication that the UE is only allowed to access 5GS via CAG cells, then the AMF rejects the NAS request and the AMF should include CAG related configuration in the NAS reject message. The AMF then release the NAS signaling connection for the UE by triggering the AN release procedure.

During transition from RRC Inactive to RRC Connected state, when the UE initiates the RRC Resume procedure for RRC Inactive to RRC Connected state transition in a CAG cell, NG-RAN shall reject the RRC Resume request from the UE if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list according to the Mobility Restrictions received from the AMF or if no Allowed CAG list has been received from the AMF. When the UE initiates the RRC Resume procedure for RRC Inactive to RRC Connected state transition in a non-CAG cell, NG-RAN shall reject the UE's Resume request if the UE is only allowed to access CAG cells according to the Mobility Restrictions received from the AMF.

During connected mode mobility procedures within NG-RAN, i.e., handover procedures, source NG-RAN shall not handover the UE to a target NG-RAN node if the target is a CAG cell and none of the CAG Identifiers supported by the target CAG cell are part of the UE's Allowed CAG list in the Mobility Restriction List or if no Allowed CAG list has been received from the AMF. Source NG-RAN shall not handover the UE to a non-CAG cell if the UE is only allowed to access CAG cells based on the Mobility Restriction List. If the target cell is a CAG cell, target NG-RAN shall reject the N2 based handover procedure if none of the CAG Identifiers supported by the CAG cell are part of the UE's Allowed CAG list in the Mobility Restriction List or if no Allowed CAG list has been received from the AMF. If the target cell is a non-CAG cell, target NG-RAN shall reject the N2 based handover procedure if the UE is only allowed to access CAG cells based on the Mobility Restriction List. When the AMF receives the Nudm_SDM_Notification from the UDM and the AMF determines that the Allowed CAG list or the indication whether the UE is only allowed to access CAG cells have changed, AMF shall update the Mobility Restrictions in the UE and NG-RAN accordingly under the conditions.

FIG. 7A illustrates a first embodiment of network and cell selection and access control of CAG cells for PNI-NPN (CAG), where access to a CAG cell is accepted. In the example of FIG. 7A, UE 711 is configured with a CAG related configuration (e.g., CAG information list 710), comprising a list of entries. For each entry, it comprises a) a PLMN ID, b) an “Allowed CAG list” having zero or more CAG-IDs, and c) an optional “indication that the UE is only allowed to access 5GS via CAG cells”. For example, entry 1 comprises PLMN 111, and an allowed CAG list with CAG-ID AAA and BBB. Through 5GC/AMF and NG-RAN, a CAG cell broadcasts one or more CAG-IDs per PLMN, e.g., CAG-ID AAA and CCC can be accessed via the CAG cell 712. As a result, UE 711 can access the CAG cell 712 in PLMN 111.

FIG. 7B illustrates a second embodiment of network and cell selection and access control of non-CAG cells, where access to a PLMN is accepted. In the example of FIG. 7B, UE 721 is configured with a CAG related configuration (e.g., CAG information list 720), comprising a list of entries. For each entry, it comprises a) a PLMN ID, b) an “Allowed CAG list” having zero or more CAG-IDs, and c) an optional “indication that the UE is only allowed to access 5GS via CAG cells”. For example, entry 1 comprises PLMN 111, and an allowed CAG list with CAG-ID AAA and BBB. In addition, there is no indication in entry 1 that indicates the UE is only allowed to access 5GS via CAG cells. Through 5GC/AMF and NG-RAN 722, UE 721 finds non-CAG cell in PLMN 111 (i.e., no CAG IDs are broadcasted by the cell 722). Since UE 721 is allowed to access 5GS via non-CAG cell, as a result, UE 721 can access the non-CAG cell 722 in PLMN 111.

FIG. 8A illustrates a first embodiment of network and cell selection and access control of CAG cells for PNI-NPN (CAG), where access to a CAG cell is rejected. In the example of FIG. 8A, UE 811 is configured with a CAG related configuration (e.g., CAG information list 810), comprising a list of entries. For each entry, it comprises a) a PLMN ID, b) an “Allowed CAG list” having zero or more CAG-IDs, and c) an optional “indication that the UE is only allowed to access 5GS via CAG cells”. For example, entry 1 comprises PLMN 111, and an allowed CAG list with CAG-ID AAA and BBB. Through 5GC/AMF and NG-RAN 812, a CAG cell broadcasts one or more CAG-IDs per PLMN, e.g., CAG-ID CCC and DDD. However, neither CAG-ID CCC nor CAG-ID DDD are in the “Allowed CAG list”. As a result, UE 811 cannot access this CAG cell CCC/DDD of PLMN 111.

FIG. 8B illustrates a second embodiment of network and cell selection and access control of CAG cells for PNI-NPN (CAG), where access to a PLMN is rejected. In the example of FIG. 8B, UE 821 is configured with a CAG related configuration (CAG information list 820), comprising a list of entries. For each entry, it comprises a) a PLMN ID, b) an “Allowed CAG list” having zero or more CAG-IDs, and c) an optional “indication that the UE is only allowed to access 5GS via CAG cells”. For example, entry 1 comprises PLMN 111, and an allowed CAG list with CAG-ID AAA and BBB. In addition, there an indication in entry 1 that indicates the UE is only allowed to access 5GS via CAG cells. Through 5GC/AMF and NG-RAN 822, UE 821 finds non-CAG cell in PLMN 111 (i.e., no CAG cell IDs are broadcasted by the cell 822). Since UE 821 is not allowed to access 5GS via non-CAG cell, as a result, UE 821 cannot access the non-CAG cell 822 in PLMN 111.

NPN (as Hosting Network) Providing Access for Localized Services.

Local or localized service is localized (i.e., provided at specific/limited area and/or can be bounded in time). The service can be realized via applications (e.g., live or on-demand audio/video stream, electric game, IMS, etc.), or connectivity (e.g., UE to UE, UE to Data Network, etc.). A localized service provider is an application provider or network operator who make their services localized and to be offered to end users via a hosting network, which is a network that provides access for local or Localized services. A home network is network owning the current in use subscription or credential of the UE. Home network can be either Home-PLMN or Subscribed-SNPN. An SNPN may support primary authentication and authorization of UEs that use credentials from a Credentials Holder using AUSF and UDM. The Credentials Holder may be Home-PLMN or Subscribed-SNPN. For SNPN as hosting network, home network can be regarded as CH. For PNI-NPN (CAG) as hosting network, home network can be regarded as (Home-)PLMN. For providing Localized services to UE, UE needs to be able to discover, select and access a NPN (as hosting network) providing access for the Localized services. The discovery mechanism is based on provisioning/(pre-)configuring/signaling the UE with appropriate information.

FIG. 9A illustrates one example of UE to discover, select and access NPN (as hosting network) and receive localized services using validity information. When UE accesses the NPN (as Hosting network) using the subscription/credentials of its home network, only two cases are considered. If Home network (/CH) is PLMN, the Hosting network can be PNI-NPN or SNPN. If Home network (/CH) is SNPN, the Hosting network can be only SNPN. If the UE accesses the Hosting network using subscriptions or credentials from the UE Home network, and the UE has multiple credentials or subscriptions, the UE needs to determine which credential or subscription to be used to access the Hosting network. Validity information or conditions information provided to the UE as part of the localized service information can be used to restrict the UE's access of the hosting network, including: (time and/or location) validity information or conditions information ((Time and/or Location:) duration, criteria, or restriction) associated with SNPN(ID) or GIN; and (time and/or location) validity information/conditions ((Time and/or Location:) duration, criteria, or restriction) associated with PNI-NPN/CAG-ID.

As depicted by 910, an SNPN-enabled UE is configured with the following information for each subscribed SNPN: PLMN ID and NID (SNPN ID) of the subscribed SNPN (e.g., SNPN 1); and Subscription identifier (SUPI) and credentials for the subscribed SNPN. If the UE supports access to an SNPN using credentials from a Credentials Holder, then the UE is also configured with 1) User controlled prioritized list of preferred SNPNs (e.g., SNPN 111, SNPN 112); 2) Credentials Holder controlled prioritized list of preferred SNPNs (e.g., SNPN 121, SNPN 122, SNPN 123); and 3) Credentials Holder controlled prioritized list of GINs (e.g., GIN 131, GIN 132).

FIG. 9B illustrates another example of UE to discover, select and access NPN (as hosting network) and receive localized services using validity information. For automatic network selection, in the case of SNPN (as hosting network) for Localized services, there can be associated (time (duration) and/or location (restriction)) validity information for SNPN(s) or GIN(s). For one example, as depicted by 910, (1)the existing Credentials Holder controlled prioritized list of preferred SNPNs (and GINs) can be extended with the (time and/or location) validity information or conditions information for each entry in the list; or as another example depicted by 911,(2)there can be a (or more) new list type defined to provide entries with validity information for SNPNs (and GINs) (ex: define new CH controlled prioritized lists of preferred SNPNs/GINs (for access localized service, where each entry contains an SNPN/GIN identity and/) including (optional) validity information/conditions).

As depicted by 910 or 911, SNPN 121 has associated time (duration) validity condition (the time duration (e.g., start and end time) in which the UE is allowed to access the SNPN 121) of January-1^(st)˜January-2^(nd), SNPN 123 has associated time validity condition of January-b 1 ^(st)˜January-3^(rd), and GIN 131 has associated time (duration) validity condition of January-b 1 ^(st)˜January-3^(rd). Such time (duration) validity/conditions information are provided to the UE as part of the localized service information to restrict the UE's access of the (hosting network) Localized services. The validity/conditions information can also optionally include location validity/conditions information, which can be in the form of geolocation and/or TAI(s)/Cell(s) (of serving network (serving PLMN/PNI-NPN or serving SNPN)), the location validity/conditions information can be used to assist the UE to know where to start searching for SNPNs hosting networks.

FIG. 9C illustrates another example of UE to discover, select and access NPN (as hosting network) and receive localized services using validity/conditions information. For automatic network selection, in the case of PNI-NPN with CAG, a CAG-ID (in the (enhanced/extended (allowed)) CAG list) can be optionally associated with time validity/conditions or restriction information (the time duration(e.g., start and end time) in which the UE is allowed to access the PNI-NPN/CAG) and/or location validity/conditions or restriction information. Time duration and/or location validity/conditions or restriction may be provided together with the CAG Identifier. For example, the ((enhance/extended) Allowed) CAG list can be provided to UE and AMF for enforcement, to make sure that UE not accessing the CAG cell outside of the time duration or(/and) outside of the allowed-location. The location validity/conditions information can be in the form of geolocation and/or TAI(s)/Cell(s) (of serving network (serving PLMN/PNI-NPN or serving SNPN)), the location validity/conditions or restriction information can be used to assist the UE to know where to start searching for the PNI-NPN hosting networks.

Note that, as depicted by 920, the (time and/or location) validity information can be stored next to the CAG-ID (e.g., enhance/extend the original allowed CAG list), or stored independently in the UE and is associated to a (or more) CAG-ID; or as depicted by 921 there can be a (or more) new list type defined to provide entries with validity information for CAG(s). As depicted by 920, for example, the ((enhanced/extended) Allowed) CAG list for PLMN 111 includes CAG AAA, BBB, and CCC. CAG-ID AAA is associated with time validity information of January-1^(st)˜January-3^(rd), and CAG-ID CCC is associated with time validity information of January-1^(st)˜January-2^(nd). Similar logic applies for location validity, if any. Such (time and location) validity conditions are provided to the UE as part of the localized service information to restrict the UE's access of the localized services (hosting network).

FIG. 10A illustrates a first example of accessing localized services via SNPN (as a hosting network), where access is accepted. In the example of FIG. 10A, UE 1001 is configured with the following SNPN subscription: the subscribed SNPN =SNPN 1, Credentials Holder controlled prioritized list of preferred SNPNs, which includes SNPN 121, SNPN 122, and SNPN 123. SNPN 121 is associated with time validity condition of January-1^(st)˜January-2^(nd), and SNPN 123 is associated with time validity condition of January-1^(st)˜January-3^(rd). Through 5GC/AMF and NG-RAN 1002, SNPN 123 broadcasts its SNPN ID==123, with an indication of access using credentials from a Credentials Holder is supported. Since UE 1001 is subscribed to SNPN 1, and SNPN 123 is included as a preferred SNPN in the entry of “list of subscriber data” for SNPN1, UE 1001 may attempt to access SNPN 123 using credentials from SNPN 1. Since a time validity condition is associated with SNPN 123, UE 1001 needs to determine whether such time validity condition is satisfied before the access. UE 1001 checks the current time of January 2^(nd), which is inside the time period of January-1^(st)˜January-3^(rd). As a result, UE 1001 can access SNPN 123 using credentials from the (subscribed) SNPN 1. SNPN 123 is the localized service provider. SNPN 123 is the hosting network. SNPN 1 is the credential holder. (If location validity information is available, in this example we assume location validity is met per the location validity information.)

FIG. 10B illustrates a second example of accessing localized services via SNPN (as a hosting network), where access is not allowed (if UE tries to access, the network will reject). In the example of FIG. 10B, UE 1001 is configured with the following SNPN subscription: the subscribed SNPN =SNPN 1, a Credentials Holder controlled prioritized list of preferred SNPNs, which includes SNPN 121, SNPN 122, and SNPN 123. SNPN 121 is associated with time validity condition of January-1^(st)˜January-2^(nd), and SNPN 123 is associated with time validity condition of January-1^(st)˜January-3^(rd). Through 5GC/AMF and NG-RAN 1002, the hosting network SNPN 123 broadcasts its SNPN ID==123, with an indication of access using credentials from a Credentials Holder is supported. Since UE 1001 is subscribed to SNPN 1, and SNPN 123 is included as a preferred SNPN in the entry of “list of subscriber data” for SNPN1, UE 1001 may attempt to access SNPN 123. However, since a time validity condition is associated with SNPN 123, UE 1001 also needs to additionally determine whether such time validity condition is satisfied before the access. UE 1001 checks the current time of January 4^(th), which is outside the time period of January-1^(st)˜January-3^(rd). As a result, UE 1001 cannot access SNPN 123 using credentials from SNPN 1.

FIG. 11A illustrates a first example of accessing localized services via PNI-NPN with CAG (as a hosting network), where access is accepted. In the example of FIG. 11A, UE 1101 is configured with a CAG related configuration 1110, comprising a list of entries. For example, entry 1 comprises PLMN 111, and an enhanced or extended allowed CAG list with CAG-ID AAA, BBB and CCC. CAG AAA is associated with time validity condition of January-1^(st)˜January-3^(rd), and CAG CCC is associated with time validity condition of January-1^(st)˜January-2nd. Through 5GC/AMF and NG-RAN 1102, a CAG cell broadcasts one or more CAG-IDs per PLMN, e.g., CAG-ID AAA of PLMN 111. Since a time validity condition is associated with CAG AAA, UE 1001 needs to determine whether such time validity condition is satisfied before the access. UE 1101 checks the current time of January 2^(nd), which is inside the time period of January-1^(st)˜January-3^(rd) associated with CAG AAA. As a result, UE 1101 can access CAG AAA of PLMN 111 via the cell. (PNI-NPN/CAG-AAA is the service provider, PNI-NPN/CAG-AAA is the hosting network, Home PLMN of the currently used USIM is the home network, and Home PLMN is the credential holder.) (If location validity information is available, in this example, we assume location validity is met per the location validity information.)

FIG. 11B illustrates a second example of accessing localized services via PNI-NPN with CAG (as a hosting network), where access is rejected. In the example of FIG. 11B, UE 1101 is configured with a CAG related configuration 1110, comprising a list of entries. For example, entry 1 comprises PLMN 111, and an enhanced or extended allowed CAG list with CAG-ID AAA, BBB and CCC. CAG AAA is associated with time validity condition of January-1^(st)˜January-3^(rd), and CAG CCC is associated with time validity condition of January-1^(st)˜January-2^(nd). Through 5GC/AMF and NG-RAN 1102, a CAG cell broadcasts one or more CAG-IDs per PLMN, e.g., CAG-ID AAA and CAG-ID CCC of PLMN 111. Since time validity conditions are associated with CAG AAA and CCC, UE 1101 needs to determine whether such time validity conditions are satisfied before the access. UE 1101 checks the current time of January 4^(th), which is outside the time period of January-1^(st)˜January-3^(rd) associated with CAG AAA, and outside the time period of January-1^(st)˜January-2^(nd) associated with CAG CCC. As a result, UE 1101 cannot access CAG cell AAA or CCC.

(5-1) Hosting Network Manual Selection and UE-Triggered Registration Update

For network and cell selection in CAG/PNI-NPN, a CAG cell shall broadcast information such that only UEs supporting CAG are accessing the cell; cells are either CAG cells or normal PLMN cells (non CAG cells). For access control, in order to prevent access to NPNs for authorized UE(s) in the case of network congestion or overload, existing mechanisms defined for Control Plane load control, congestion and overload control can be used, as well as the access control and barring functionality, or Unified Access Control using the access categories can be used. The Mobility Restrictions shall be able to restrict the UE's mobility according to the (Allowed) CAG list (if configured in the subscription) and include an indication whether the UE is only allowed to access 5GS via CAG cells (if configured in the subscription). When a UE supports accessing hosting network, CAG/PNI-NPN can be selected as hosting network for localized services. When taking hosting network functionality into account, the UE needs to trigger mobility and periodic registration update procedure under certain circumstances.

In accordance with one novel aspect, a method of enhanced manual network selection procedure for access localized services in PNI-NPN is proposed. For manual CAG/PNI-NPN selection as hosting network, if a CAG cell in a PLMN broadcasting a CAG-ID is available and included in the (Allowed) CAG-ID list of the UE-stored CAG related configuration of the PLMN, the user may manually select the CAG ID. However, the CAG-ID that is associated with validity information, and the corresponding validity criteria may or may not be satisfied, e.g., due to the UE-stored CAG related configuration is different from the NW-maintained CAG related configuration. Therefore, the UE does not know whether, from network's point of view, the CAG cell is suitable or not. In response, the UE triggers a registration procedure for mobility and periodic registration update, to confirm with the network whether the UE is allowed to access the network through this CAG cell (if NW allows, NW sends REGISTRATION ACCEPT, otherwise the NW sends, e.g., REGISTRATION REJECT and optionally including the updated CAG related configuration to the UE).

FIG. 12 illustrates an example sequence flow between a UE and a PLMN network for performing manual network selection, where the UE selects a CAG/PNI-NPN as hosting network and triggers a mobility and periodic registration update procedure. In step 1211, UE 1201 is camped on a first CAG cell and is registered in a first PLMN1 CAG-1. The first CAG cell is a suitable CAG cell, e.g., providing access for localized services and acted as a non-hosting network, and CAG-1 is not associated with any validity information. In step 1221, UE 1201 maintains a CAG related configuration, which includes a list of Allowed CAG list for a corresponding PLMN. For example, the Allowed CAG list may include CAG-1 and CAG-2 for PLMN1. In step 1222, UE 1201 receives a list of supported CAG IDs (e.g., CAG-2) broadcasted by a second CAG cell.

In step 1231, user of UE 1201 enables manual network selection mode and manually selects the CAG-2 (i.e., CAG broadcasted by second CAG cell) (of PLMN 1). The second CAG cell broadcasts a CAG ID (CAG-2) that is included in the list of Allowed CAG IDs of the first PLMN1, and per the maintained CAG related configuration the AS layer of UE 1201 assumes the second CAG cell to be a suitable cell. In step 1241, however, UE 1201 determines that CAG-2 is associated with validity information, and corresponding validity criteria are not met, e.g. a timer validity information does not match the current UE time. However in the NW side the CAG-2 validity criteria may be met, and this may be because the UE-stored CAG related configuration and the NW-maintained CAG related configuration are not synchronized. Therefore, in step 1251, UE 1201 triggers a registration update procedure to confirm with the network, by sending a registration update request message. In step 1252, UE 1201 receives a registration update accept message, which optionally carries an update CAG related configuration. The registration update procedure is for mobility registration update and periodic registration update, which allows the UE to confirm whether the UE can access the selected CAG cell (e.g., if NW confirms UE can access, the NW sends accept message, otherwise the NW sends reject message), and to update with the latest NW-maintained CAG related configuration. UE 1201 can decide to remain in the second CAG cell or perform a network/cell selection based on the updated configuration.

FIG. 13 illustrates examples of a Manual Network Selection Mode Procedure that is triggered by user, and the user manually selects a CAG/PNI-NPN candidates as hosting network for localized services. In general, a CAG related configuration includes zero or more entries, each entry containing a) a PLMN ID, b) an ((enhanced/extended) Allowed) CAG list having zero or more CAG-IDs, and c) an optional indication that the UE is only allowed to access 5GS via CAG cells. In the example of FIG. 13 , UE 1301 maintains a CAG related configuration 1310 for accessing localize services via PNI-NPN with CAG (as a hosting network). The CAG related configuration 1310 contains multiple entries. Under entry 1, the CAG-ID list of PLMN 222 includes CAG 21, CAG 22, and CAG 23. CAG 21 and CAG 23 are not associated with any validity information, and CAG 22 is associated with time validity information, e.g., time validity (duration restriction) criteria of January-5^(th) 20:00 pm˜22:00 pm (as depicted by 1322).

In manual NPN selection, a first CAG cell 1302 in PLMN 222 broadcasts a list of supported CAG-IDs, e.g., CAG 21, a second CAG cell 1303 in PLMN 222 broadcasts a list of supported CAG-IDs, e.g., CAG 22. Further, if the broadcasted CAG-IDs (e.g., CAG 21 and CAG 22) are included in the UE-stored CAG related configuration 1310, then UE 1301 may find the CAG cells 1302 and 1303 to be available for selection. For example, UE may first camps on CAG cell 1302 and then manually select CAG cell 1303 later. However, if the CAG-ID (e.g., CAG 22) is associated with validity information based on the UE-stored CAG related configuration, then such CAG may not be authorized if the validity criteria are not met. For example, if the current time is January 4, then the time duration restriction associated with CAG 22 does not match with the UE's current time. As a result, CAG 22 is not authorized for access (according to UE's maintained CAG related configuration). UE 1301 thus needs to trigger a registration update procedure, even if the second CAG-ID (CAG 22) is in the allowed CAG list in the CAG related configuration maintained by the UE, and even if first CAG cell 1302 and second CAG cell 1303 belong to the same TAI and traditionally no MRU is needed.

FIG. 14 is a flow chart of a method for Manual Network Selection when user selects a CAG/PNI-NPN as hosting network and triggers registration update procedure in accordance with one novel aspect. In step 1401, a UE maintains a Closed Access Group (CAG) related configuration for network selection, wherein the CAG related configuration comprises an Allowed CAG list of a second PLMN, and wherein the UE is registered in a first PLMN through a first CAG cell. In step 1402, the UE determines that a second CAG-ID is broadcasted by a second CAG cell in the first PLMN (or another second PLMN, e.g., equivalent PLMN), and the second CAG-ID is included in the Allowed CAG list of the first PLMN (or another second PLMN, e.g., equivalent PLMN). In step 1403, the UE triggers a manual network selection by a user of the UE, wherein the user manually selects the (the first or second PLMN and) the second CAG-ID. In step 1404, the UE triggers a registration update procedure upon determining that the second CAG-ID is associated with validity information, and corresponding validity criteria associated with the second CAG-ID are not met based on the validity information.

Although the present invention has been described in connection with certain specific embodiments for instructional purposes, the present invention is not limited thereto. Accordingly, various modifications, adaptations, and combinations of various features of the described embodiments can be practiced without departing from the scope of the invention as set forth in the claims. 

What is claimed is:
 1. A method, comprising: maintaining a Closed Access Group (CAG) related configuration for network selection by a user equipment (UE), wherein the CAG related configuration comprises an Allowed CAG list of a second PLMN, and wherein the UE is registered in a first PLMN through a first CAG cell; determining that a second CAG-ID is broadcasted by a second CAG cell of a second PLMN, and the second CAG-ID is included in the Allowed CAG list of the second PLMN; triggering a manual network selection by a user of the UE, wherein the user manually selects the second CAG-ID; and triggering a registration update procedure upon determining that the second CAG-ID is associated with validity information, and corresponding validity criteria associated with the second CAG-ID are not met based on the validity information.
 2. The method of claim 1, wherein the first PLMN and second PLMN is the same PLMN, or the first PLMN and second PLMN are different PLMNs.
 3. The method of claim 1, wherein the validity information includes at least one of time validity information and location validity information.
 4. The method of claim 3, wherein the second CAG-ID of the second PLMN is not authorized when the time validity information does not match a current time of the UE or when the location validity information does not match a current location of the UE.
 5. The method of claim 1, wherein the registration update procedure is for mobility and periodic registration update.
 6. The method of claim 5, wherein the UE obtains an updated CAG related configuration from the network via the registration update procedure.
 7. The method of claim 5, wherein the UE triggers the registration update procedure when there is no tracking area change from the first CAG cell to the second CAG cell.
 8. The method of claim 1, wherein the validity information includes only time validity information, wherein the validity criteria are met if the time validity information matches a current time of the UE, and wherein the validity criteria are not met if the time validity information does not match the current time of the UE.
 9. The method of claim 1, wherein the validity information includes only location validity information, wherein the validity criteria are met if the location validity information matches a current location of the UE, and wherein the validity criteria are not met if the location validity information does not match the current location of the UE.
 10. The method of claim 1, wherein the validity information includes both time validity information and location validity information, wherein the validity criteria are met if the time validity information matches a current time of the UE and the location validity information matches a current location of the UE, and wherein the validity criteria are not met if the time validity information does not match the current time of the UE or the location validity information does not match the current location of the UE.
 11. A User Equipment (UE), comprising: a Closed Access Group (CAG) information handling circuit that maintains a CAG related configuration for network selection, wherein the CAG related configuration comprises an Allowed CAG list of a second PLMN, and wherein the UE is registered in a first PLMN through a first CAG cell; a control circuit that determines that a second CAG-ID is broadcasted by a second CAG cell in the second PLMN, and the second CAG-ID is included in the Allowed CAG list of the second PLMN; a network selection circuit that triggers a manual network selection by a user of the UE, wherein the user manually selects the second CAG cell of the second PLMN; and a registration circuit that triggers a registration update procedure upon determining that the second CAG-ID is associated with validity information, and corresponding validity criteria associated with the second CAG-ID are not met based on the validity information.
 12. The UE of claim 11, wherein the first PLMN and second PLMN is the same PLMN, or the first PLMN and second PLMN are different PLMNs.
 13. The UE of claim 11, wherein the validity information includes at least one of time validity information and location validity information.
 14. The UE of claim 12, wherein the second CAG-ID of the PLMN is not authorized when the time validity information does not match a current time of the UE or when the location validity information does not match a current location of the UE.
 15. The UE of claim 11, wherein the registration update procedure is for mobility and periodic registration update.
 16. The UE of claim 15, wherein the UE obtains an updated CAG related configuration from the network via the registration update procedure.
 17. The UE of claim 15, wherein the UE triggers the registration update procedure when there is no tracking area change from the first CAG cell to the second CAG cell.
 18. The UE of claim 11, wherein the validity information includes only time validity information, wherein the validity criteria are met if the time validity information matches a current time of the UE, and wherein the validity criteria are not met if the time validity information does not match the current time of the UE.
 19. The UE of claim 11, wherein the validity information includes only location validity information, wherein the validity criteria are met if the location validity information matches a current location of the UE, and wherein the validity criteria are not met if the location validity information does not match the current location of the UE.
 20. The UE of claim 11, wherein the validity information includes both time validity information and location validity information, wherein the validity criteria are met if the time validity information matches a current time of the UE and the location validity information matches a current location of the UE, and wherein the validity criteria are not met if the time validity information does not match the current time of the UE or the location validity information does not match the current location of the UE. 